TrustRadius Insights
HBase has established itself as a crucial tool for various organizations, including PayPal, to store and retrieve records in near real …
Overview
What is HBase?
The Apache HBase project's goal is the hosting of very large tables -- billions of rows X millions of columns -- atop clusters of commodity hardware. Apache HBase is an open-source, distributed, versioned, non-relational database modeled after Google's Bigtable.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Popular Features
- Availability (5)7.878%
- Security (5)7.878%
- Performance (5)7.171%
- Concurrency (5)7.070%
Pricing
N/A
Unavailable
What is HBase?
The Apache HBase project's goal is the hosting of very large tables -- billions of rows X millions of columns -- atop clusters of commodity hardware. Apache HBase is an open-source, distributed, versioned, non-relational database modeled after Google's Bigtable.
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
23 people also want pricing
Alternatives Pricing
What is MarkLogic Server?
MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities. The vendor states it is the most secure multi-model database, and it’s deployable in any environment. They state it is an ideal database to power a data hub.
What is Couchbase Capella?
The Couchbase Capella product is a fully managed DBaaS automating setup and ongoing operations.
Product Demos
Apache Hbase Tutorial | Hadoop Hbase | Hbase Training | Intellipaat
YouTube
Features
Return to navigation
Product Details
- About
- Tech Details
- FAQs
What is HBase?
HBase Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Frequently Asked Questions
The Apache HBase project's goal is the hosting of very large tables -- billions of rows X millions of columns -- atop clusters of commodity hardware. Apache HBase is an open-source, distributed, versioned, non-relational database modeled after Google's Bigtable.
Reviewers rate Scalability highest, with a score of 8.6.
The most common users of HBase are from Mid-sized Companies (51-1,000 employees).
Comparisons
Compare with
Reviews and Ratings
(32)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Recommendations
HBase has established itself as a crucial tool for various organizations, including PayPal, to store and retrieve records in near real time. Users have found that HBase excels in analytical use cases by providing faster lookup of records with consistent reads and writes, making it ideal for handling large datasets. It allows for faster querying of records compared to other NoSQL databases, resulting in improved data access and analysis capabilities. The ease of installation and configuration, thanks to its integration with the HDP Hortonworks stack, is another advantage that users appreciate.
One significant use case for HBase is as a data store for streaming data ingested through mechanisms like Apache NiFi, Apache Storm, Apache Spark Streaming, Apache Flink, and Streaming Analytics Manager. This allows organizations to efficiently manage and process continuous streams of data. Furthermore, HBase's ability to store structured, semi-structured, and unstructured data without requiring a pre-defined schema makes it a versatile choice for a range of applications.
Customers across industries have leveraged HBase successfully for their specific needs. In the retail sector, it serves as a datastore for product catalogs, session management systems, and revenue-generating platforms. Additionally, businesses involved in advertising and location analytics rely on HBase to generate locational information efficiently. Its scalability and read performance with avro data containing geospatial information make HBase preferable over alternatives like Cassandra.
HBase also plays a vital role in managing data within Apache Hadoop systems. It is used to create master data sets and reconcile conflicting data. Moreover, HBase serves as a secondary layer of storage that consolidates updates from upstream key-value stores.
While users highly recommend HBase for its data model consistency, scalability, and well-documented features, they do acknowledge the operational overhead associated with deploying and managing clusters. Nonetheless, this does not overshadow the significant benefits that organizations derive from using HBase to solve scalability and management issues related to multi-terabyte applications.
HBase is recommended for handling huge amounts of data and integrating with other tools. Users find HBase to be a good choice for scenarios requiring streaming ingest, fast lookups, and processing massive datasets. Its integration capabilities with other tools make it a valuable asset for organizations dealing with vast amounts of data.
HBase is also highly regarded for its real-time reporting capabilities over big data and seamless integration with business intelligence (BI) tools. Users recommend HBase as a reliable NoSQL datastore specifically designed to handle big data loads. It serves as an effective solution for storing unstructured or semi-structured data while providing easy integration with frontend applications.
Another common recommendation is to consider HBase's native integration with Hadoop and other data access engines. Users find HBase helpful for storing and processing non-relational data efficiently. Additionally, they recommend it as a reliable option for data storage and provision to other applications, making it suitable for various use cases.
It is important to evaluate HBase when considering NoSQL databases, as it offers unique benefits such as amazing structured/unstructured data storage capabilities and support for parallel programming. Users suggest utilizing HBase for specific use cases where large amounts of similar data need to be stored and accessed easily.
Lastly, users emphasize the importance of proper data modeling and workload tuning for successful implementation of HBase. They advise against using HBase for full table scan workloads and suggest considering relational databases when applicable. Additionally, they encourage the use of HBase for OLAP and OLTP use cases, highlighting its suitability for handling huge datasets and analytical processing needs.
Attribute Ratings
Reviews
(1-4 of 4)Companies can't remove reviews or game the system. Here's why
December 13, 2018
HBASE!!!
HBase is used as part of the company's main revenue generating platform. We're using it store data with usages of mapreduce, generates locational information for advertising business and location analytics. Storage wise, it made sense to use HBASE over Cassandra, as well as for read performance with avro data with geospatial information in the data
- Excellent for read performance
- Great store of file format of avro
- Easy integration into mapreduce
- Replication ability
- Write performance
- Performance support for parquet file format. supports, but performance wise still not there
- API / library availability for spark, rather than creating a new library for it
60%
6.0
- Negative ROI has been on hardware usage. When used frequently, we have had constant disk failures. As a result, it requires HDD replacements.
- But with disk failures, HA is available, however, to a certain extent.
- Large datasets helped causality issues to be mitigated.
Cassandra os great for writes. But with large datasets, depending, not as great as HBASE. Cassandra does support parquet now. HBase still performance issues. Cassandra has use cases of being used as time series. HBase, it fails miserably. GeoSpatial data, Hbase does work to an extent. HA between the two are almost the same.
April 19, 2018
No SQL Database to Support Near Real Time Analytics
HBase was used in my previous organization(PayPal) where we needed a database for storing and retrieving records in near real time. It was used within consumer analytics and other sub-teams. It supported our near real-time use analytical cases by proving a faster lookup of records with consistency reads/writes. Apart from that, helped in querying the records much faster than other NoSQL databases.
- Faster lookup of records using the row keys. It helped to fetch thousands of records in a much faster way using the row keys
- As it is a columnar data store, helped us to improve the query performance and aggregations
- Sharding helps us to optimize the data storage and retrieval. HBase provides automatic or manually sharding of tables.
- Dynamic addition of columns and column family helped us to modify the schema with ease.
- Identified issues with Hmaster when handling a huge number of nodes
- Cannot have multiple indexes as row key is the only column which could be indexed.
- HBase does not support partial row keys which limit its query performance.
75.71428571428571%
7.6
- It supports the near real-time use cases when integrated with Spark Streaming.
- It helps to store huge volume of records with consistent reads/writes.
- Maintenance is the pain point as it requires some maintenance and monitoring of regional servers and nodes
Compared NoSQL databases with traditional databases for faster retrieval and consistency. As MongoDB is a NoSQL supports dynamic fields, however, query performance is bad for aggregations and added maintenance. When compared with MySQL and Teradata, it could not scale up as fast as Hbase and added cost involved to it. HBase can be easily scalable to a huge volume of records, have a faster lookup and provides consistency
September 13, 2017
HBase
HBase solves problems of scalability and management of multi-terabyte applications. It makes scaling to +1 nodes very easy, especially through Ambari. It is built with fault tolerance and availability in mind. You can use it on a single node but it shines on multi-node infrastructure. With high data access speed and resiliency, I wouldn't recommend any other NoSQL database for general use.
- HBase data access and retrieval only gets better with larger scale.
- Fault tolerance is built in, if you have unreliable hardware, HBase will make every effort to keep your data online.
- Extremely fast key lookups and write throughput.
- Multi-tenancy is still work in progress
- Usability and beginner friendliness
- It has a bad reputation of being complex
- We were able to scale our application from 5TB running in a relational database to 20TB on top of HBase
- Application availability was always high even with half of the nodes having hardware issues
- HBase can be used with standard mechanical harddrive storage. There's no need for fancy SAN or NAS storage with HBase which is almost always expensive.
Typically, Cassandra is faster on reads and HBase is faster on writes. You use Cassandra when you want to use a website, HBase is just an overall good general use database engine. Cassandra has its own storage engine and HBase uses HDFS and all its benefits. MongoDB is typically also used in web development, it has a great support for JSON but it's been known for poor scalability. It also uses its own storage engine.
November 25, 2015
Apache HBase: Through the Looking Glass!
Apache HBase was used for mastering solutions, for creating master data sets and reconciling conflicting data coming to Apache Hadoop systems.
- Apache HBase is a widely used java based distributed NoSQL environment on Apache Hadoop.
- While there has been growing interest and efforts in in memory computing, there are investments on Apache Hadoop (or hadoop provider variants) across domains. So that is a large market.
- I worked on HBase for applications which needed to provide strong consistency and interact with Apache Hadoop.
- You could encounter issues like region is not online or NotServingException or region server going down, out of memory errors.
- As HBase works with Zookeeper, care needs to be taken it is correctly set up. Most issues pertain usually to environment setup, configuration, shared load on system or maintenance.
- The performance across workloads when evaluated against other NoSQL variants was not best in class, this is most times okay, but can be improved.
- If you use Apache HBase, and want to upgrade it for some features then you might need to do a compatibility check against your Apache Hadoop and Apache HBase versions, there are dependency to think about.
- The HBase master slave becomes the single point of failure, and may not be a preferred design.It is not highly available system.
- Last I checked it did not have well tested easy integrations with Spark, and that can help.
- Faster data insights
- Better customer service